home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1994 March
/
Internet Info CD-ROM (Walnut Creek) (March 1994).iso
/
inet
/
ietf
/
dns
/
dns-minutes-92jul.txt
< prev
next >
Wrap
Text File
|
1993-02-17
|
3KB
|
80 lines
Editor's Note: Revised minutes 9/4/92
CURRENT_MEETING_REPORT_
Reported by Win Treese/DEC
Minutes of the Domain Name System Working Group (DNS)
Win Treese chaired the meeting, as the regular Chair, Mike Reilly, could
not attend.
Agenda
o The proposed DNS MIB. (Jon Saperia, DEC)
o The NSAP resource record proposal. (RFC1348)
o Possible guidelines for the assignment of names in top-level
domains. (Mike St. Johns, Dept. of Defense)
DNS MIB
Jon Saperia handed out copies of the Internet Draft DNS MIB, which had
previously been sent to the namedroppers mailing list. Jon had made
several changes based on comments from the meeting in San Diego. There
were a few minor comments, which Jon agreed to incorporate.
There was some discussion of whether or not SNMP should be used to
update authoritative date in a server. Jon Saperia and Rob Austein
pointed out that this is a hard problem. Adding a new host, for
example, involves adding new address and pointer records, and possibly
HINFO and MX records. Should the server store the updated information
in its permanent database? How are all replicas updated? Is the update
protocol atomic for all replicas? Is it atomic at a single replica?
How are changes authenticated and authorized?
The Group awaits a proposal on updates; the MIB will be moved forward as
it is now.
NSAP Resource Records
Bill Manning presented RFC1348, which proposes new resource records for
NSAPs to support RFC1347 (the TUBA proposal). There were some minor
suggestions for modifications to the proposal. We also discussed having
a wildcard address query for any type of addresses. The Group concluded
that it was best not to create a new class for extended addresses of any
type, since the class mechanisms are not well-understood in practice.
Naming Guidelines
Mike St. Johns proposed establishing some naming guidelines for the
top-level domains (e.g., COM, EDU), because they are growing quite
rapidly, and may eventually overwhelm the capabilities of both humans
1
and computers to use them. There was quite a bit of discussion on this
issue, but very little was resolved. A detailed proposal of guidelines
is probably needed to further the discussion.
Attendees
Robert Austein sra@epilogue.com
David Borman dab@cray.com
Lida Carrier lida@apple.com
Walter Lazear lazear@gateway.mitre.org
Bill Manning bmanning@rice.edu
Michael Patton map@lcs.mit.edu
Mike St. Johns stjohns@umd5.umd.edu
Jon Saperia saperia@tcpjon.ogo.dec.com
Win Treese treese@crl.dec.com
2